HyperBEAM Getting Started

Get started with HyperBEAM development using modern patterns. This guide covers the essential steps to go from basic AO knowledge to building HyperBEAM-powered applications.

Prerequisites

You should have completed the Welcome & Quick Start guide and have:

• AOS installed and connected to HyperBEAM
• Basic understanding of AO processes and handlers
• Familiarity with Lua basics

Step 1: Connect to HyperBEAM

Make sure you're connected to the HyperBEAM network:

aos --node https://forward.computer

If you're already running aos, you can verify your connection by checking your process ID and ensuring it's working with HyperBEAM patterns.

Step 2: Understand Exposing Process State via HTTP

The key difference with HyperBEAM is exposing your process state via HTTP instead of requiring slow dry-run messages.

Old Way (Legacynet)

-- Slow: Clients must send dry-run messages
Handlers.add(
  "GetCounter",
  Handlers.utils.hasMatchingTag("Action", "GetCounter"),
  function(msg)
    return msg.reply({ Data = tostring(Counter) })
  end
)

New Way (HyperBEAM)

-- Fast: Expose state via HTTP
Handlers.add(
  "Increment",
  Handlers.utils.hasMatchingTag("Action", "Increment"),
  function(msg)
    Counter = Counter + 1

    -- Expose updated counter via HTTP
    Send({
      device = 'patch@1.0',
      counter = Counter
    })
  end
)

Step 3: Your First HyperBEAM Process

Let's create a counter process that builds on the basics from the welcome guide:

-- Initialize state
Counter = Counter or 0

-- Initial state sync - makes state available immediately
InitialSync = InitialSync or 'INCOMPLETE'
if InitialSync == 'INCOMPLETE' then
  Send({
    device = 'patch@1.0',
    counter = Counter
  })
  InitialSync = 'COMPLETE'
end

-- Increment handler with enhanced state exposure
Handlers.add(
  "Increment",
  Handlers.utils.hasMatchingTag("Action", "Increment"),
  function(msg)
    Counter = Counter + 1

    -- Expose new value with metadata
    Send({
      device = 'patch@1.0',
      counter = Counter,
      lastUpdate = os.time(),
      updatedBy = msg.From
    })

    print("Counter incremented to:", Counter)
  end
)

Step 4: Test Your Process

1. Load the process into your AOS session
2. Increment the counter:

   Send({ Target = ao.id, Tags = { Action = "Increment" } })

3. Read via HTTP:

    curl https://forward.computer/YOUR_PROCESS_ID~process@1.0/compute/counter

You should see the counter value returned instantly via HTTP!

Step 5: Access Multiple State Values

You can expose multiple values at once:

-- Expose multiple related values
Send({
  device = 'patch@1.0',
  counter = Counter,
  status = "active",
  metadata = {
    version = "1.0.0",
    owner = ao.id,
    created = os.time()
  }
})

Access them via:

• /compute/counter - Returns the counter value
• /compute/status - Returns the status
• /compute/metadata - Returns the metadata object

Step 6: Update State on Changes

Always expose updated state after modifications:

Handlers.add(
  "UpdateStatus",
  Handlers.utils.hasMatchingTag("Action", "UpdateStatus"),
  function(msg)
    local newStatus = msg.Tags.Status

    if not newStatus then
      return msg.reply({ Error = "Status required" })
    end

    Status = newStatus

    -- Expose updated status
    Send({
      device = 'patch@1.0',
      status = Status,
      statusUpdated = os.time(),
      updatedBy = msg.From
    })

    return msg.reply({ Status = "Updated" })
  end
)

Best Practices

1. Always use lowercase keys in cache tables (HTTP paths are case-insensitive)
2. Avoid reserved keywords like state, info, test, now, compute
3. Batch updates when possible for efficiency
4. Initialize state sync for critical data that should be available immediately
5. Expose derived values (like counts, totals) for easier frontend access

Common Application Patterns

For real-world application patterns like token transfers, chat systems, and data structures, see Building with HyperBEAM which covers comprehensive examples for production use cases.

Next Steps

Now that you understand the basics of exposing process state via HTTP, explore:

• Core Concepts - Deep dive into technical details, edge cases, and advanced patterns
• Building Applications - Real-world patterns for tokens, chat, and web integration
• Migration Guide - If you have existing Legacynet processes to migrate

Need Help?

• Join the Discord community
• Check the HyperBEAM documentation
• Browse the Tutorials for hands-on projects